[material_ui] Standardize M3 and M3E token template base class names - #12675
Merged
Conversation
…lutter#12209) As title. Related to flutter/flutter#187899 ## Pre-Review Checklist - [x] I read the [Contributor Guide] and followed the process outlined there for submitting PRs. - [x] I read the [AI contribution guidelines] and understand my responsibilities, or I am not using AI tools. - [x] I read the [Tree Hygiene] page, which explains my responsibilities. - [x] I read and followed the [relevant style guides] and ran [the auto-formatter]. - [x] I signed the [CLA]. - [x] The title of the PR starts with the name of the package surrounded by square brackets, e.g. `[shared_preferences]` - [x] I [linked to at least one issue that this PR fixes] in the description above. - [x] I followed [the version and CHANGELOG instructions], using [semantic versioning] and the [repository CHANGELOG style], or I have commented below to indicate which documented exception this PR falls under[^1]. - [x] I updated/added any relevant documentation (doc comments with `///`). - [x] I added new tests to check the change I am making, or I have commented below to indicate which [test exemption] this PR falls under[^1]. - [ ] All existing and new tests are passing.
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Code Review
This pull request renames the template classes M3TokenTemplate and M3ETokenTemplate to TokenTemplateM3 and TokenTemplateM3E, and updates the generated file naming convention from *_m3_defaults.g.dart to *_defaults_m3.g.dart. The corresponding tests and test fixtures have been updated to reflect these changes. Feedback is provided regarding a missing blank line between test blocks in the test suite to maintain consistency and readability.
Comment on lines
148
to
149
| }); | ||
|
|
||
| test('will run dart format over the generated file', () { |
Contributor
There was a problem hiding this comment.
For better readability and consistency with the rest of the test suite, please maintain a blank line between the test blocks.
Suggested change
| }); | |
| test('will run dart format over the generated file', () { | |
| }); | |
| test('will run dart format over the generated file', () { |
github-actions
Bot
added
p: material_ui
triage-design
QuncCccccc
approved these changes
Aug 31, 2026
QuncCccccc
left a comment
QuncCccccc
left a comment
Contributor
There was a problem hiding this comment.
LGTM! Thank you for the help!
elliette
added
the
autosubmit
QuncCccccc
added
override: no versioning needed
This was referenced Sep 1, 2026
pull Bot
pushed a commit
to g-star1024/flutter
that referenced
this pull request
Sep 1, 2026
…r#192119) flutter/packages@d642322...7a7912f 2026-09-01 21270878+elliette@users.noreply.github.com [material_ui] Migrate AppBar M3 template to use new gen_defaults script (flutter/packages#12707) 2026-09-01 32538273+ValentinVignal@users.noreply.github.com [vector_graphics] Fix deprecation lints (flutter/packages#12702) 2026-08-31 21270878+elliette@users.noreply.github.com [material_ui] Standardize M3 and M3E token template base class names (flutter/packages#12675) 2026-08-31 32538273+ValentinVignal@users.noreply.github.com [vector_graphics_compiler] Fix deprecation issues in tests (flutter/packages#12700) 2026-08-31 stuartmorgan@google.com [google_maps_flutter] Convert marker controllers to Swift (flutter/packages#12662) 2026-08-31 jmccandless@google.com [material_ui, cupertino_ui, go_router] Command to test dart fixes (flutter/packages#12390) 2026-08-31 engine-flutter-autoroll@skia.org Roll Flutter from c978386 to c8c5e3b (4 revisions) (flutter/packages#12706) 2026-08-31 269567208+reidbaker-agent@users.noreply.github.com [tool] Exempt AGENTS.md from version and changelog checks (flutter/packages#12681) If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/flutter-packages-flutter-autoroll Please CC flutter-ecosystem@google.com on the revert to ensure that a human is aware of the problem. To file a bug in Flutter: https://github.com/flutter/flutter/issues/new/choose To report a problem with the AutoRoller itself, please file a bug: https://issues.skia.org/issues/new?component=1389291&template=1850622 Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Work towards flutter/flutter#191088
Ports over #12209 which landed on the
m3e_migrationfeature branch.Original PR description
As title. Related to flutter/flutter#187899
Pre-Review Checklist
[shared_preferences]///).If you need help, consider asking for advice on the #hackers-new channel on Discord.
Note: The Flutter team is currently trialing the use of Gemini Code Assist for GitHub. Comments from the
gemini-code-assistbot should not be taken as authoritative feedback from the Flutter team. If you find its comments useful you can update your code accordingly, but if you are unsure or disagree with the feedback, please feel free to wait for a Flutter team member's review for guidance on which automated comments should be addressed.Footnotes
Regular contributors who have demonstrated familiarity with the repository guidelines only need to comment if the PR is not auto-exempted by repo tooling. ↩ ↩2